some software that claims to support the reading of TIFF images is
incapable of reading images in anything but the native CPU byte order on
which the software was written. (Especially notorious are applications
written to run on Intel-based machines.) By default the library will
create new files with the native byte-order of the CPU on which the
application is run. This ensures optimal performance and is portable to
any application that conforms to the TIFF specification. To force the
library to use a specific byte-order when creating a new file the ``b''
and ``l'' option flags may be included in the call to open a file; for
example, ``wb'' or ``wl''.
RRRREEEETTTTUUUURRRRNNNN VVVVAAAALLLLUUUUEEEESSSS
Upon successful completion _T_I_F_F_O_p_e_n, _T_I_F_F_F_d_O_p_e_n, and _T_I_F_F_C_l_i_e_n_t_O_p_e_n
return a TIFF pointer. Otherwise, NULL is returned.
DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
All error messages are directed to the _T_I_F_F_E_r_r_o_r(3T) routine. Likewise,
warning messages are directed to the _T_I_F_F_W_a_r_n_i_n_g(3T) routine.
""""%%%%ssss"""":::: BBBBaaaadddd mmmmooooddddeeee. The specified _m_o_d_e parameter was not one of ``r''
(read), ``w'' (write), or ``a'' (append).
%%%%ssss:::: CCCCaaaannnnnnnnooootttt ooooppppeeeennnn. _T_I_F_F_O_p_e_n() was unable to open the specified filename
for read/writing.
CCCCaaaannnnnnnnooootttt rrrreeeeaaaadddd TTTTIIIIFFFFFFFF hhhheeeeaaaaddddeeeerrrr. An error occurred while attempting to read the
header information.
EEEErrrrrrrroooorrrr wwwwrrrriiiittttiiiinnnngggg TTTTIIIIFFFFFFFF hhhheeeeaaaaddddeeeerrrr. An error occurred while writing the default
header information for a new file.
NNNNooootttt aaaa TTTTIIIIFFFFFFFF ffffiiiilllleeee,,,, bbbbaaaadddd mmmmaaaaggggiiiicccc nnnnuuuummmmbbbbeeeerrrr %%%%dddd ((((0000xxxx%%%%xxxx)))). The magic number in the
header was not (hex) 0x4d4d or (hex) 0x4949.
NNNNooootttt aaaa TTTTIIIIFFFFFFFF ffffiiiilllleeee,,,, bbbbaaaadddd vvvveeeerrrrssssiiiioooonnnn nnnnuuuummmmbbbbeeeerrrr %%%%dddd ((((0000xxxx%%%%xxxx)))). The version field in the
CCCCaaaannnnnnnnooootttt aaaappppppppeeeennnndddd ttttoooo ffffiiiilllleeee tttthhhhaaaatttt hhhhaaaassss ooooppppppppoooossssiiiitttteeee bbbbyyyytttteeee oooorrrrddddeeeerrrriiiinnnngggg. A file with a
byte ordering opposite to the native byte ordering of the current machine
was opened for appending (``a''). This is a limitation of the library.